Managing image storage size

ABSTRACT

A system and method for managing image storage size. The invention uses reduction criteria to determine how much to reduce the storage size of an image over time. In one embodiment, reduction of data storage size includes degrading the quality of the image. The reduced-size image replaces the image from the previous iteration. The smaller storage allows longer access to the information in quick access storage and quicker transmission time.

BACKGROUND OF THE INVENTION

[0001] 1. Technical Field

[0002] The present invention relates generally to image data, and moreparticularly, to a system and method for managing image storage size.

[0003] 2. Related Art

[0004] With the Internet becoming an integral part of life, the abilityto provide adequate data storage for image inventories is increasinglyimportant. One exemplary industry where image inventory storage size isincreasingly important is the United States banking industry. In thisindustry, digitized, compressed documents are initially stored inwrite-once media and archived for the legally required seven years.Documents to be imaged are generally created with strong (high contrast)information such as letters and correspondence with printed text andpossibly a company logo. Some documents have background scenes, e.g.,checks, but the vital information is usually printed in black orhandwritten in blue or black ink. One common compression standard usedis that promulgated by the Joint Photographic Experts Group (JPEG).Despite advanced compression techniques, a typical digital check record,which includes a header followed by compressed image segments of thefront and back of the check, results in an average total record size of40-50 kilobytes. Since there are approximately 80 billion checks writtenper year in the United States, the image inventory for seven yearstranslates into 23,000-28,000 trillion bytes of compressed data for asingle copy. Even a smaller bank's portion of this data is large.

[0005] In addition to the archived version, many banks also provideonline document images of, for example, the preceding three months, toallow quick access by commercial and individual customers. Hence, twocopies of at least a portion of a bank's image inventory are oftenmaintained, which creates shortages of data storage. One mechanism toreduce online image storage requirements and allow online document imageselection is through the use of a visual index of thumbnails such asdisclosed in U.S. Pat. No. 6,154,295 to Freuland et al. In this setting,the customer can order additional copies of data from the “index” print.However, both the high resolution image and the dimension-reducedthumbnail are later discarded.

[0006] Magnifying the data storage problem is that many industriesincreasingly want to provide access to imaged documents for largerperiods of time. For example, in the banking industry, it is preferredto provide imaged documents online for at least the past fifteen and ahalf months (i.e., from January of one year to the subsequent year'sApril) for tax purposes. Unfortunately, the increased data storagerequirements make this service difficult to provide.

[0007] One mechanism some banks use to provide three months worth ofimaged documents online is providing a small amount of images online(e.g., one month's worth) and using batch processes to an archiveversion for older images. However, batch processing creates otherproblems. One problem is that a batch process can take long periods oftime to complete. Since customers would like to be able to browse and doresearch quickly, batch processing for older imaged documents isunacceptable. For example, an item cleared six months ago can take up toa week or longer to retrieve. Moreover, a first inquiry some times doesnot lead to the correct item being retrieved. In addition, the banksoftentimes charge the customers a large service fee for its efforts toretrieve the image from the archive version. In summary, batchprocessing-based image retrieval is inefficient and slow, and is not anadequate remedy for reducing image inventory size.

[0008] Another potential remedy to storage requirements is to providefurther data compression. However, since continuous-tone compressiontechniques (e.g., JPEG) are generally lossy processes, care must betaken less increased compression removes vital information. By “lossy”is meant that the decompressed image is not quite the same as theinitial image. In some applications, such as in the banking industry,document information must be maintained. Lossless methods for reducingstorage size of an image are available but require increasing thecomplexity of the lossless compression technique used such astranscoding from generic Huffman tables to custom Huffman tables (i.e.,Huffman tables tuned for each image), and transcoding from Huffmanentropy coding to arithmetic entropy coding.

[0009] Another banking industry objective that is hindered by imageinventory storage requirements is the ability to use imaged documents inday-to-day clearing operations. Currently one type of clearing operationis completed by providing document images on a compact disk (CD) tocommercial customers. This means that hundreds of CDs are mailed tocommercial customers every day, which increases the bank's operationalexpenses. Consequently, commercial customers expenses are high for thisessential service, since the commercial banks often confirm the checksare not fraudulent before authorizing payment.

[0010] Another problem related to image inventory data storage size isthat of quick transmission of images. The larger the size of image(s),the longer it takes to transmit.

[0011] The above-described problems in the banking industry are alsofound in other industries where image inventories are used. Otherexemplary industries include: photography developers, photographic newsagencies, catalog shopping, other Internet-based activities, old booksscanned by libraries, scanned ledgers, genealogy material, businessrecords, and all incoming mail for paperless office environments.

[0012] In many of these industries, pages are scanned in and the primaryinterest is in the content rather than the presentation. In these cases,optical character recognition (OCR) may have been applied to the scannedimages in order to capture as much of the critical information aspossible and convert it into coded text such as ASCII characters so textsearch and data mining techniques can be applied. Unfortunately, the OCRerror rate is still significant. Having easy access to the poorerquality, but still legible image of the original document would assistquickly settling accuracy questions.

[0013] In view of the foregoing, there is a need in the art for a systemand method for managing an image data storage size, such as thoseprovided online, to reduce storage requirements, increase transmissionspeed, and meet customer requirements.

SUMMARY OF THE INVENTION

[0014] The invention is a system and method for reducing data storagesize of image inventory based on reduction criteria. Reduction occurs asa recursive degrading of image quality. One benefit of the invention isthat it allows the time an image inventory can be provided online to beextended, and the communication costs and bandwidth to be reduced.Another benefit of the invention is that, for images online, it reducesoperational cost and thus the fees. Further, it provides for a periodicmaintenance process which recursively reduces image inventory size, andthus optionally allows more space for new additions to the inventory.Access to a high quality image (i.e., legal archived version) can bemaintained. Even a low quality image created using the invention issufficient to confirm that it is the desired image so that errors inbatch-fetching the highest quality version are avoided. Transmissionspeed of an image is also increased using the invention.

[0015] A first aspect of the invention is directed to a method formanaging an image of an object stored in a database, the methodcomprising the steps of: reducing a storage size of the image from abase level to at least one secondary level based on reduction criteria,wherein each secondary level is smaller in storage size than the baselevel.

[0016] A second aspect of the invention is directed to a method ofmanaging storage size of an image of an object, wherein the image isaccessed by a user, the method comprising the steps of: reducing thestorage size of the image based on reduction criteria to create asize-reduced version; allowing user access to the size-reduced versionfor a predetermined duration; and repeating the steps of reducing andallowing after expiration of the predetermined duration.

[0017] A third aspect of the invention includes a system for managingstorage size of an image of an object where the image is accessed by auser online, the system comprising: a size-reduction evaluator toperiodically evaluate whether the image is subject to a size reductionbased on size-reduction criteria; and a size reducer to reduce the sizeof the image based on instructions from the size-reduction evaluator.

[0018] A fourth aspect of the invention provides a system for managingstorage size of an image of an object, wherein the image is accessed bya user, the system comprising: means for evaluating the image based onreduction criteria to determine whether to reduce the data storage sizeof the image, leave the image alone or purge the image; and means forreducing the data storage size of the image based on the results of themeans for evaluating.

[0019] A fifth aspect of the invention is directed to a computer programproduct comprising a computer useable medium having computer readableprogram code embodied therein for managing a size of a stored image thatis accessible to a user, the computer program product comprising:program code configured to evaluate the image based on reductioncriteria to determine whether to reduce the data storage size of theimage, leave the image alone or purge the image; and program codeconfigured to reduce the data storage size of the image based on theresults of the evaluating.

[0020] The foregoing and other features and advantages of the inventionwill be apparent from the following more particular description ofpreferred embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The preferred embodiments of this invention will be described indetail, with reference to the following figures, wherein likedesignations denote like elements, and wherein:

[0022]FIG. 1 shows a block diagram of an exemplary environment where theinvention finds applicability;

[0023]FIG. 2 shows a block diagram of an image management system of FIG.1;

[0024]FIG. 3 shows a flow diagram of the logic of an image datamanagement system of FIG. 2; and

[0025] FIGS. 4-11 show a progressively reduced-in-size image createdaccording to the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0026] For convenience purposes only, the following description includesthe following subtitles:

[0027] I. Introduction

[0028] II. Image Capture System

[0029] III. Data Management System (DMS)

[0030] A. Process and DMS Logic

[0031] B. Reduction Criteria

[0032] C. Exemplary Operation

[0033] IV. Alternatives and Other System Components

[0034] I. Introduction

[0035]FIG. 1 is a block diagram of one exemplary environment in whichthe present invention is applicable. In this setting, customer(s) oruser(s) 2 access an entity 3 web server 4 in a known fashion to viewstored images online that are part of an image inventory stored in adatabase 5. Entity 3 may be any institution that makes images availableonline. Images, as used herein, may be of any object and may includemultiple parts. For purposes of this disclosure, the invention will bedescribed with entity 3 as a financial institution such as a bank.Likewise, images will be described in terms of bank-related documentssuch as checks. The multiple parts of imaged checks may include aheader, an image portion (e.g., check background art) and a textportion. User(s) 2 access is over known networks such as a local areanetwork (LAN), wide area network (WAN) and/or the Internet. Onepreferred access mechanism is the Internet.

[0036] Web server 4 includes, or can access, database(s) 5. Database 5may include an archive version 6 of a complete image inventory and anactive, or online, version 7 of at least part of the complete imageinventory. Archive version 6, which is optional, includes images thatare stored for long periods of time, and generally are in a write once,read only form. For financial institutions, archived images may be ofany document that must be stored for a legally mandated duration, e.g.,seven years. Negotiable instruments such as checks are one of these typedocuments. It should be recognized that archived version 6, althoughshown for clarity to be part of database 5, may be stored in a varietyof manners. One other common storage technique for archive version 6 iscompact disc read only memory (CD ROM). Entity 3 also includes an imagemanagement system 8 capable of attaining images of object(s) 9 via animage capture device 10 and managing image inventory storage size. Imagemanagement system 8 interacts with database(s) 5 to control image datastorage. System 8 may be part of web server 4, but in one preferredembodiment is a separate system.

[0037] Turning to FIG. 2, image management system 8 preferably includesa memory 12, a central processing unit (CPU) 14, input/output devices(I/O) 16 and a bus 18. A database 20 may also be provided for temporarystorage of image data and other data relative to processing tasks.Memory 12 preferably includes a program product 22 that, when executedby CPU 14, comprises various functional capabilities described infurther detail below. Memory 12 (and database 20) may comprise any knowntype of data storage system and/or transmission media, includingmagnetic media, optical media, random access memory (RAM), read onlymemory (ROM), a data object, etc. Moreover, memory 12 (and database 20)may reside at a single physical location comprising one or more types ofdata storage, or be distributed across a plurality of physical systems.CPU 14 may likewise comprise a single processing unit, or a plurality ofprocessing units distributed across one or more locations. A servercomputer typically comprises an advanced mid-range multiprocessor-basedserver, such as the RS6000 from IBM, utilizing standard operating systemsoftware, which is designed to drive the operation of the particularhardware and which is compatible with other system components and I/Ocontrollers. I/O 16 may comprise any known type of input/output deviceincluding a network system, modem, keyboard, mouse, scanner, voicerecognition system, CRT, printer, disc drives, image capture device 10,etc. Additional components, such as cache memory, communication systems,system software, etc., may also be incorporated into system 8.

[0038] As shown in FIG. 2, program product 22 may include an imagecapture system 24, a data management system 26, and other systemcomponent(s) 28.

[0039] II. Image Capture System

[0040] Image capture system 24 may be implemented in a variety of forms.For example, in terms of the banking industry, system 24 may be part ofa high speed, high volume document processing system such as found ininstitutional banks. For example, system 24 may be implemented as partof an IBM 3897 Image Capture System. In another environment, imagecapture system 24 may be personal computer scanner software.

[0041] III. Data Management System

[0042] As shown FIG. 2, data management system (DMS) 26 includes astorage module 30, a designation module 32, a size reduction evaluationmodule 34 and a size reduction module 36. The functions of thesecomponents will become apparent via the following discussion of DMS 26logic.

[0043] A. Process and DMS Logic

[0044] Turning to FIG. 3, the inventive process will be described ingreater detail relative to the logic of DMS 26.

[0045] In a first precursor step S1, an object 9 (FIGS. 1 and 2) isimaged via image capture system 24 in a known fashion.

[0046] In step S2, a designation for each image is assigned bydesignation module 32. The designation indicates the status of the imagebased on non-real time reduction criteria. An image designation ispreferably stored in a header portion of the image and is based on atleast one reduction criteria 21 (FIG. 2). Reduction criteria, as will bediscussed in greater detail below, are factors that determine to whatextent the data storage size of an image can be reduced, e.g., overtime. The factors that make up the reduction criteria can be selectivelychosen and, hence, can differ from entity-to-entity, object-to-object,etc. A designation may be in the form of a simple list of reductioncriteria values or may be a specially created alpha-numeric codeindicative of reduction criteria values.

[0047] In step S3, the image is stored by storage module 30 during whichthe storage module may interact with image capture module 24. Storagemodule 30 creates a compressed, substantially lossless quality version,i.e., nearly photographic level, of the image. As indicated above, as anoption, a copy of the image may be stored in archive version 6 (FIG. 1)and maintained for access by a user upon request. In the financialinstitution setting, archive version 6 is generally used for long termstorage of documents that are legally mandated to be stored for longperiods of time. One general duration is of seven years. As analternative, when a user requests access to archive version, the usermay include an indication of the duration that the archive version willbe required.

[0048] Compression can be completed according to any now known or laterdeveloped standard. One preferred standard is that promulgated by theJoint Photographic Experts Group (JPEG). The image maybe compressedanywhere from 10:1 to 20:1 ratio such that it includes minimal artifacts(e.g., noise in high contrast regions, blocking in gray regions) andlegible text, if any. Although compressed, image data storage sizeremains relatively large.

[0049] In addition to storage in archive version 6, in our exemplaryenvironment, storage module 30 stores a compressed, substantiallylossless quality version of the image in active version 7 (FIG. 1) foraccess by user(s) 2. In a financial institution, the above step mayinclude, for example, daily storage of “on us” checks and otherdocuments.

[0050] In step S4, a user 2 is allowed to access the image in activeversion 7 in a known fashion. For example, user 2 may access web server4 over the Internet and view images stored in active (online) version 7via his/her browser or a graphical user interface (not shown) of entity3. If an archive version 6 is maintained, user 2 may also request animage from archive version 6 of the image at any time. The archiveversion of the image may then replace a corresponding reduced-sizedimage in active version 7. When a user requests access to archiveversion 6, the user may include an indication of the duration that thehigh-quality active version of the image will be required. If activeversion 7 of the image is not for user access, e.g., online, the processwould skip step S4 and proceed with step S5. Statistical data regardinguser access and/or image utilization may be kept during this time forcomparison with the reduction criteria.

[0051] In step S5, an image is evaluated by size reduction evaluationmodule 34. Evaluation can result in the following results: the image isleft alone, the image is reduced in size or the image is purged. Inaddition, evaluation determines to what extent an image is reduced basedon reduction criteria 21 and predetermined reduction/purging rules 23(FIG. 1) that instruct size reduction module 36.

[0052] In an initial evaluation, reduction may include a specialreduction processing. For instance, a portion of the image may bepurged. For example, the image portion may be purged while the textfields are maintained. This purging of the image portion is advantageouswhere, for example, the image portion is provided for aesthetic purposesonly. In terms of a check, text fields may include such information asamount, payor, payee, date, account number, and check number(s). Thetext information is helpful for doing research, and allows monitoringfor long term patterns that can be used to detect suspicious orfraudulent use.

[0053] Actual evaluation may take a variety of forms. In one preferredembodiment, evaluation includes review of the image designation, whichindicates the status of the image relative to non-real time reductioncriteria, i.e., factors that do not change over time. Evaluation thendetermines what reduction or purging, if any, is required based on theimage designation and the predetermined reduction/purging rules 23. Forinstance, in the banking industry, a designation noting that the imageis for a user having substantial monetary amounts (one reductioncriteria factor) held by the bank may have no reduction conducted, i.e.,a reduction/purging rule mandates no reduction for an image exhibitingthat reduction criteria factor. In contrast, an image for a user havinga history of little or no use of active version 7 may be reduced to avery small sized image, i.e., one with lower quality. In addition,evaluation may include review of real-time reduction criteria, i.e.,factors that change over time, such as available storage space, andprior reduction based on related reduction/purging rules 23.

[0054] In an alternative embodiment, designation step S2 may be skipped,and evaluation module 34 may evaluate the image according to reductioncriteria 21 on a real time basis. That is, each time an evaluation isconducted, each image is analyzed relative to reduction criteria 21 todetermine what, if any, reduction or purging is required.

[0055] Regardless of evaluation type, evaluation module 34 determinesthe state of each image relative to reduction criteria 21 and determinesthe applicable reduction/purging rule 23 to be implemented by sizereduction module 36, at step S6. When reduction is necessary, sizereduction module 36 undertakes the reduction operation. For purposes ofthis disclosure, the term “reduction” shall refer to the decreasing ofthe data storage size and not necessarily the actual dimensional sizereduction of the image. “Reduction” includes any data compressiontechnique so long as selections on image degradation, e.g., imagelegibility and quality, can be made even though the degradation may notbe apparent to the human eye. Furthermore, “reduction” includes reducingand replacement of the starting image with the reduced image. Incontrast, current techniques make a copy of the starting image and applyreduction techniques to the copy, which increases data storagerequirements. This is especially inefficient where an archive version ismaintained because three copies are present: the archive version, theactive version (possibly an online version) and the reduced version.According to the invention, the copy of the active version is reducedand replaced, creating two copies if an archive version is maintainedand one copy if an archive version is not maintained.

[0056] In one embodiment, reduction includes a process of entropydecoding the image, changing quantized coefficients and quantizationtables (Q-tables), and entropy recoding the image, as described inrelated U.S. patent application Ser. No. 09/760,383, entitled “EnhancedCompression of Documents,” which is hereby incorporated by reference.This changing of the quantized coefficients and quantization tables actsas a selective dynamic range reduction in a preprocessing step beforeJPEG encoding. Quantization tables are replaced after encoding withscaled-up quantization values, and any JPEG decoder can restore thedynamic range. Using this enhanced compression technique, an image isretrieved and restored with less bytes, and accordingly, lower quality.

[0057] In an alternative embodiment, reduction of the image can beaccomplished with further compression, for example, using the JPEGbaseline (DCT-based with Huffman coding), JPEG DCT-based with arithmeticcoding, or the JPEG 2000 (wavelet-based with arithmetic coding)compression standards with larger quantization values. This process ofincreasing the lossliness of the compression, however, must be usedcautiously where legibility of the information must be maintained.

[0058] Other alternatives for reducing the stored image size include:changing the number of horizontal samples, number of vertical lines,number of bits (precision) per sample, number of components, the size ofthe quantization, the type of compression (lossless to lossy), orchanging the lossliness of the compression technique.

[0059] The above-described reduction techniques can be appliedindividually or in an arbitrary combination to achieve a desiredreduction in storage size. For instance, each reduction/purging rule 23may implement a particular combination of reduction techniques based onthe reduction criteria.

[0060] If evaluation determines that purging is necessary, sizereduction module 36 undertakes the purging operation. Once an image hasbeen saved for any mandated time frame and/or has achieved a qualitylevel where no further reduction is advisable (see, for example, theimage of FIG. 11), a final step of evaluating/reducing would includepurging.

[0061] Once reduction/purging is complete, at step S7, the image, if notpurged, is again stored. In the case where the image inventory isavailable online, storage would be to active version 7.

[0062] At step S8, if active version 7 of the image is for user access,a user would again be allowed to access images, e.g., online. Again, ifan archive version 6 is maintained, a user 2 may also request an archiveversion, i.e., high quality version, of the image at any time. Thearchive version of the image may then replace a correspondingreduced-sized image in active version 7. When a user requests access toarchive version 6, the user may include an indication of the durationthat the high-quality active version of the image will be required.Statistical data regarding user access and/or image utilization may alsobe kept during this time for comparison with the reduction criteria. Asshown in FIG. 7, the image is of lower quality but maintains itslegibility. As will be described below, further reduction, e.g.,decompression, additional dynamic range reduction, and recompressioncycles, would further reduce data storage requirements.

[0063] In step S9, a determination of whether a predetermined durationhas expired is made by image management system 26. The predeterminedduration sets how much time passes between evaluations. Accordingly, anentity 3 can set evaluations to occur, for example, weekly, monthly,quarterly, etc. When the predetermined duration has expired, the processreturns to step S5 for further evaluation, which can provide furtherreduction of image(s) based on the reduction criteria. When thepredetermine duration has not expired, the process returns to step S8and a user's access is continued.

[0064] B. Reduction Criteria:

[0065] As noted above, the reduction criteria are factor(s) thatdetermine to what extent the data storage size of an image can bereduced. Factors that make up the reduction criteria can be selectivelychosen and, hence, a wide variety of unique reduction criteria arepossible. For example, reduction criteria may vary fromentity-to-entity, image-to-image, user-to-user, etc. Further, somefactors are based on real-time attributes and, hence, change over time.For example, such factors (described below) as: available data storage,suspicious activity, time since object creation and time since objectimaging vary over time.

[0066] In terms of a financial institution, the reduction criteria mayinclude, for example, the following factors:

[0067] 1. Available data storage.

[0068] 2. Time since creation and/or deposit (i.e., imaging) of object(document). For example, the creation date probably determines intowhich income tax year the document falls. The depositing date determinescritical time periods after the depositing (e.g., the three days forcrediting an account with the dollar amount).

[0069] 3. Prior size reduction. This factor indicates the stage oflegibility versus storage size of the image. At some stage furtherreduction will hurt legibility too much and purging the image may be abetter choice.

[0070] 4. Utilization or access history of the object (document),account and/or user. Statistical data such as the history of a user'sonline utilization may be an excellent indicator of future demand. Forexample, a user that has never requested an image from active version 7indicates a non-computer user. For such accounts, the bank may want toimmediately store only the lowest quality images. On the other hand, foran account with a history of problems and many requests for the backs ofchecks, the highest quality may be available longer. In addition, sometypes of documents may be accessed more often than other types ofdocuments.

[0071] 5. Object (document) value. Documents for large dollar amountsare a small percentage of all checks, but have exceptional value and arekept at the highest quality for longer.

[0072] 6. Type of account. For example, a commercial account may beprovided higher quality images than an individual account. Further,accounts with only a few checks may have them stored with better qualitythan accounts with many checks so that the storage per account is keptmore uniform.

[0073] 7. Volume of objects (e.g., checks) per user account.

[0074] 8. User's total account value. A user's total account value maywarrant providing extra services.

[0075] 9. User selections of options and/or profile input. The user mayknow what options he/she is likely to need or use. In this instance, afinancial institution can allow user(s) 2 to submit profiles and/orselect their desired image reduction options. In one example, a userrequest for the high-quality archive version of an image may include anindication of the time for which the high-quality version should beavailable in active version 7. An authenticated version direct fromentity 3 may be requested for a much-reduced fee under suchcircumstances.

[0076] 10. User fees paid. Users could be charged fees for improvedtime/quality of the online image service. This factor may apply, forexample, to commercial accounts where the convenience of quality onlineimages may actually save time and money.

[0077] 11. User account history. This factor may indicate whether theaccount has had fraudulent activities conducted thereon. Accounts withsuspicious activity (i.e. sudden change in check amounts and usagepatterns) and accounts that have been red-flagged may be kept morecarefully to allow later audits and more on-demand information. Forexample, where a user request a high-quality archive version, and thathigh-quality image replaces the current active version, thathigh-quality image may be kept longer in active version 7 because it wasspecifically requested.

[0078] 12. Object part imaged. For example, the front of a checkcontains key information and is generally of higher contrast than theback of the checks. Thus, the fronts of checks may be further reducedmore safely than the backs of checks. Also private individuals with poorrecord keeping skills are more likely to want to see the fronts of theirchecks than the bank endorsements on the back of their checks. For suchindividual accounts, the banks may discard the back of the checks in theactive version 7 much earlier than the fronts.

[0079] The above-described financial institution reduction criteria arenot exhaustive.

[0080] It should be recognized that other industries may have differentreduction criteria. For example, a photograph developer may havedifferent priorities and, hence, different criteria.

[0081] C. Exemplary Operation

[0082] In our exemplary banking industry environment, as noted above, atypical bank would capture and archive compressed, but substantiallylossless quality versions of documents such as checks on a daily basis.Once archived, active version 7 is updated to include these same images.Periodically (e.g., monthly or quarterly) active version 7 is evaluated.To make room for the new images, individual images are either: leftalone, reduced or purged.

[0083] Referring to FIGS. 4-11, exemplary images created by a bankaccording to the invention are shown. For purposes of description,images having differing quality and/or legibility and, hence, differingdata storage size, may be described as being part of a “level.”Continuing with our example, a bank may include a base level and atleast one secondary level of images as outlined in the following table:Image Image Level Image Quality Image Legibility Storage Size Base LevelHigh High Large Secondary Level 1 Medium High Middle Secondary Level 2Low-medium Medium-high Small Secondary Level 3 Low Medium Very small

[0084] The base level of images refers to those images stored in archiveversion 6, and initially stored in active version 7. FIG. 4 shows anexample of this type image. The first level images are preferably incompressed format, e.g., a JPEG format. Each secondary level of imagesis a size-reduced version of the images based on the reduction criteriaand stored in active version 7. As indicated, there may be a number ofsecondary levels that each represent an iteration of reduction on aparticular image. However, movement from one level to another moresize-reduced level does not necessarily have to be sequentially throughthe indicated levels, e.g., reduction may reduce an image from the baselevel to secondary level 3, skipping secondary levels 1 and 2.

[0085] In the instant case, three secondary levels are present. Eachsecondary level preferably includes different quantization tables thanevery other secondary level and the base level. Hence, a first secondarylevel (1) exhibits lower image quality compared to the base level; asecond secondary level (2) exhibits lower image quality compared to thefirst secondary level (1); and the third secondary level (3) exhibitslower image quality compared to the second secondary level (2).FIGS. 5and 6 represent exemplary secondary level 1 images; FIGS. 7 and 8represent exemplary secondary level 2 images; and FIGS. 9 and 10represent exemplary secondary level 3 images. FIG. 11 represents animage where further reduction is probably inadvisable, and the imagewould be purged.

[0086] Actual stored image sizes, in bytes, for FIGS. 4-11 using Huffmancoding and arithmetic coding are as follows: FIG.: Huffman CodingArithmetic Coding 11 3,717 1,216 10 4,823 2,649 9 6,775 4,880 8 8,6666,621 7 10,260 8,190 6 11,766 9,604 5 13,143 10,989 4 14,553 12,306

[0087] In accordance with our hypothetical example, a bank may includein its (simplified) reduction criteria that accounts having over $10,000in them will be treated as elite users and, hence, provided high qualityimages for longer periods of time. Similarly, users with less than$10,000 will be provided only the highest quality images for a shorterperiod. The bank may then provide base level images to elite users forone (1) month duration from the time of capture. The bank may thenimplement reduction/purging rules to drop the image(s) to secondarylevel 1 for the next eleven (11) months duration and finally tosecondary level 3 for the next six (6) years duration. For the non-eliteuser, the bank may implement reduction/purging rules to providesecondary level 1 for the first month, secondary level 2 for the nextmonth and secondary level 3 for the next six (6) years. Note that at alltimes, any user can request a high quality, substantially losslessquality image from archive version 6.

[0088] Using the above system and method, each entity can efficientlyreduce data storage space for images based on their own reductioncriteria. In addition, each entity can implement reduction criteria andreduction/purging rules tailored to their industry and customers. As aresult, each entity can provide images online for longer periods oftime, increase transmission speed of images and provide better customerservice.

[0089] IV. Alternatives and Other System Components:

[0090] The invention has been described in terms of a periodicevaluation function. It is also possible to further reduce requestedimages on-the-fly to decrease download time. For example, a bankingcustomer could request the lowest quality image to visually confirm theamount fields for their trusted/known/long-time payees and the highestquality for new payees at download time. The reduced quality imagescould be stored simultaneously and in a few days the original quality(if not requested) could be discarded.

[0091] The invention has been described relative the image inventorythat is stored in an archive version 6 and an active version 7, withevaluation occurring on the active version. The evaluation and reductiontechniques of the invention, however, can be applied to any image orimage inventory (or part thereof) regardless of whether it is madeavailable online. Hence, the teachings of the invention should not belimited to application to online image inventories.

[0092] The invention has been described in terms of the banking industrywith documents such as checks, credit card receipts, stocks and bonds,etc. The same system and method can work for other image inventorieswhere the need for high quality images may lessen over time. One suchapplication could be an online photograph library of current events. Ifan indication of where the highest quality/archived copy can be obtainedis still available with the low quality images, the low quality imagescan help to decide which larger, higher quality images need to bedownloaded. Hence, the library can offer reduced quality images forresearch/browsing purposes, which reduces data storage needs, and havethe high quality version stored for access when desired. Once the usercompletes their research, a high quality image can always be requestedfrom the library archives.

[0093] Another application is helping individuals manage image data sizeon a personal computer. For example, where individuals upload theirdigital images to their web sites, in order to keep the total storagesize down, the user could (or have a system 26) further reduce the olderimages based on reduction criteria.

[0094] Images stored to different levels of quality may also be storedwith different entropy coding or compression algorithms. The JPEGbaseline requires the use of Huffman coding. In this invention, customHuffman tables are allowed. However, further compression without anychange in quality is possible with the arithmetic entropy coding option.Generally, the smaller the compressed stored image size the larger theimprovement because the Huffman codes are limited to integer bits percode word and require at least one bit for each symbol. The arithmeticcoding does not have this limitation and can code effectively to theentropy limit. Unfortunately, most web browsers do not support thisoption today so additional recoding may be needed. In addition, theoriginal images may have been lossy JPEG baseline compressed. Afterseveral iterations, lossy compression may no longer be acceptable. Alossless or near lossless algorithm such as JPEG LS may be choseninstead.

[0095] The components of the invention including, for example, imagemanagement system 8 and data management system 26, may be used alone orwith other system components 28. Other system components 28 may includeany well known document processing system components, e.g., an imagecapture processor, alteration indicating system, etc. One exemplarysystem component 28 is a statistical tracking system to keep statisticaldata about the retrieval usage of images over time to help makedecisions regarding the reduction criteria and when to further reduce orpurge image data.

[0096] An image authentication system can also be added for security.For example, visible and invisible watermarks can be implemented. Othermethods can be used to authenticate that a reduced image, although notthe highest quality nor the archived version, came from the originatingentity and is an authorized version. Optionally, the images can containa uniform resource locator (URL) link back to a higher quality version(e.g., in archive version 6) with appropriately secure access.Traceability of the recursively reduced image can also be an optionalpart of the authentication system.

[0097] In the previous discussion, it will be understood that the methodsteps discussed preferably are performed by a processor, such as CPU 14of system 8, executing instructions of program product 22 stored inmemory. It is understood that the various devices, modules, mechanismsand systems described herein may be realized in hardware, software, or acombination of hardware and software, and may be compartmentalized otherthan as shown. They may be implemented by any type of computer system orother apparatus adapted for carrying out the methods described herein. Atypical combination of hardware and software could be a general-purposecomputer system with a computer program that, when loaded and executed,controls the computer system such that it carries out the methodsdescribed herein. Alternatively, a specific use computer, containingspecialized hardware for carrying out one or more of the functionaltasks of the invention could be utilized. The present invention can alsobe embedded in a computer program product, which comprises all thefeatures enabling the implementation of the methods and functionsdescribed herein, and which—when loaded in a computer system—is able tocarry out these methods and functions. Computer program, softwareprogram, program, program product, or software, in the present contextmean any expression, in any language, code or notation, of a set ofinstructions intended to cause a system having an information processingcapability to perform a particular function either directly or after thefollowing: (a) conversion to another language, code or notation; and/or(b) reproduction in a different material form.

[0098] While this invention has been described in conjunction with thespecific embodiments outlined above, it is evident that manyalternatives, modifications and variations will be apparent to thoseskilled in the art. Accordingly, the preferred embodiments of theinvention as set forth above are intended to be illustrative, notlimiting. Various changes may be made without departing from the spiritand scope of the invention as defined in the following claims.

What is claimed is:
 1. A method for managing an image of an objectstored in a database, the method comprising the steps of: reducing astorage size of the image from a base level to at least one secondarylevel based on reduction criteria, wherein each secondary level issmaller in storage size than the base level.
 2. The method of claim 1,further comprising the step of repeating the step of reducing to reducethe storage size of the image from one secondary level to anothersecondary level based on the reduction criteria.
 3. The method of claim2, wherein the step of repeating occurs after expiration of apredetermined duration.
 4. The method of claim 1, wherein the image isof a document.
 5. The method of claim 1, wherein the base level is acompressed format and each secondary level has a different Q-table thanthe base level.
 6. The method of claim 5, wherein the compressed formatis a JPEG baseline compression format.
 7. The method of claim 5, whereinthe compressed format is a JPEG 2000 compression format.
 8. The methodof claim 5, wherein the at least one secondary level includes at leasttwo secondary levels, each secondary level having a different Q-tablethan every other secondary level.
 9. The method of claim 8, wherein afirst secondary level exhibits lower image quality compared to the baselevel; and a second secondary level exhibits lower image qualitycompared to the first secondary level.
 10. The method of claim 9,wherein the at least two secondary levels includes at least threesecondary levels; and a third secondary level exhibits lower imagequality compared to the second secondary level.
 11. The method of claim1, wherein the image includes a plurality of images.
 12. The method ofclaim 1, wherein the step of reducing includes compressing the image.13. The method of claim 1, wherein the image is in a compressed formatand the step of reducing includes entropy decoding the image, changingquantized coefficients and quantization tables, and entropy recoding theimage.
 14. The method of claim 1, wherein an initial step of reducingincludes deleting a portion of the image.
 15. The method of claim 1,wherein the reduction criteria includes at least one of: available datastorage, time since object creation, time since object imaging, priorsize reduction, prior access by user, object value, user account type,volume of objects per user account, user total account value, a userselection, user fees paid, user account history, suspicious activity andobject part imaged.
 16. The method of claim 1, further comprising thestep of maintaining a copy of image at the base level.
 17. The method ofclaim 16, further comprising the step of replacing the image at thesecondary level with a copy of the image at the base level when a userrequests access to the copy of the image at the base level.
 18. Themethod of claim 17, wherein the user includes an indication of theduration that the base level will be required when the user requests thecopy of the image at the base level.
 19. The method of claim 1, whereina final step of reducing includes purging the image.
 20. The method ofclaim 1, further comprising the step of maintaining statistical data forcomparison with the reduction criteria.
 21. A method of managing storagesize of an image of an object, wherein the image is accessed by a user,the method comprising the steps of: reducing the storage size of theimage based on reduction criteria to create a size-reduced version;allowing user access to the size-reduced version for a predeterminedduration; and repeating the steps of reducing and allowing afterexpiration of the predetermined duration.
 22. The method of claim 21,wherein the step of reducing includes compressing the image.
 23. Themethod of claim 21, wherein the image is in a compressed format and thestep of reducing includes achieving more compression.
 24. The method ofclaim 23, wherein the step of reducing includes entropy decoding theimage, changing quantized coefficients and quantization tables, andentropy recoding the image.
 25. The method of claim 21, wherein aninitial step of reducing includes deleting a portion of the image. 26.The method of claim 21, wherein the reduction criteria includes at leastone of: available data storage, time since object creation, time sinceobject imaging, prior size-reduction, prior access by user, objectvalue, user account type, volume of objects per user account, user totalaccount value, user selections, user fees paid, user account history,suspicious activity and object side imaged.
 27. The method of claim 21,further comprising the step of maintaining a substantially losslessquality version of the image.
 28. The method of claim 27, furthercomprising the step of allowing the user to access the substantiallylossless quality version upon request.
 29. The method of claim 21,wherein a final step of reducing includes purging the image.
 30. Asystem for managing storage size of an image of an object where theimage is accessed by a user online, the system comprising: asize-reduction evaluator to periodically evaluate whether the image issubject to a size reduction based on size-reduction criteria; and a sizereducer to reduce the size of the image based on instructions from thesize-reduction evaluator.
 31. The system of claim 30, further comprisinga designator to assign the image a designation indicative of the statusof the image based on the size-reduction criteria.
 32. The system ofclaim 31, wherein the size-reduction criteria includes at least one of:prior size-reduction, prior access by user, object value, user accounttype, volume of objects in user account, user total account value, auser selection, user fee paid, user account history and object sideimaged.
 33. The system of claim 32, wherein the size-reduction criteriaincludes real-time factors including at least one of: available datastorage, suspicious activity, time since object creation and time sinceobject imaging.
 34. The system of claim 30, further comprising a storagemodule to save a substantially lossless quality version of the image.35. The system of claim 30, wherein the size-reduction evaluatordetermines whether to leave the image alone, reduce the storage size ofthe image or purge the image.
 36. The system of claim 30, wherein afirst activation of the size reducer purges an image portion of theimage.
 37. The system of claim 30, wherein the image is in a compressedformat and the size reducer is adapted to decode the image, change adynamic range scaling of the image, and recode the image.
 38. The systemof claim 30, wherein the size-reduction evaluator determines areduction/purging rule to be followed by the size reducer based on thereduction criteria.
 39. A system for managing storage size of an imageof an object, wherein the image is accessed by a user, the systemcomprising: means for evaluating the image based on reduction criteriato determine whether to reduce the data storage size of the image, leavethe image alone or purge the image; and means for reducing the datastorage size of the image based on the results of the means forevaluating.
 40. A computer program product comprising a computer useablemedium having computer readable program code embodied therein formanaging a size of a stored image that is accessible to a user, thecomputer program product comprising: program code configured to evaluatethe image based on reduction criteria to determine whether to reduce thedata storage size of the image, leave the image alone or purge theimage; and program code configured to reduce the data storage size ofthe image based on the results of the evaluating.